MME overload or underload mitigation by MME VNF apparatus and method

ABSTRACT

Embodiments of the present disclosure describe apparatuses and methods for mobility management entity (MME) overload or underload mitigation using an MME virtual network function (VNF). Various embodiments may include one or more processors to execute instructions to process a notification from a virtual network function manager (VNFM) to determine instantiation of a MME as a VNF, add the MME to an MME pool, and assign a value to an application parameter of the MME VNF. Other embodiments may be described and/or claimed.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication No. 62/133,023, filed Mar. 13, 2015, entitled “METHOD ANDAPPARATUS OF MME OVERLOAD OR UNDERLOAD MITIGATION BY MME VNF IN THE LTENETWORKS”, the entire disclosure of which is hereby incorporated byreference in its entirety for all purposes, except for those sections,if any, that are inconsistent with this specification.

FIELD

Embodiments of the present disclosure generally relate to the field ofwireless communication, and more particularly, to apparatuses andmethods for enabling Mobility Management Entity (MME) functionality.

BACKGROUND

The background description provided herein is for generally presentingthe context of the disclosure. Unless otherwise indicated herein, thematerials described in this section are not prior art to the claims inthis application and are not admitted to be prior art or suggestions ofthe prior art, by inclusion in this section.

MME load balancing and rebalancing functions help direct a UserEquipment (UE) in an MME pool area to an appropriate MME in a mannersuch that the UE to MME connections are evenly distributed among MMEs inthe MME pool. In existing network configurations, the MMEs are physicalnetwork functions (PNFs) such that the number of MMEs in the MME pool isstatic and an MME can be overloaded as the number of UEs entering thenetwork keeps rising. Existing MME overload control uses Non-AccessStratum (NAS) signaling to reject NAS requests from UEs, which can causeservice degradation to subscribers.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 schematically illustrates a hybrid management system for managingboth non-virtualized and virtualized networks in accordance with variousembodiments.

FIG. 2 is a diagram illustrating an MME overload mitigation processusing an MME virtual network function (VNF) in accordance with variousembodiments.

FIG. 3 is a diagram illustrating an MME VNF contraction process inaccordance with various embodiments.

FIG. 4 is a block diagram of a device with electronic device circuitryin accordance with various embodiments.

FIG. 5 is a block diagram of an example computing device that may beused to practice various embodiments described herein.

FIG. 6 illustrates an article of manufacture having programminginstructions, incorporating aspects of the present disclosure, inaccordance with various embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B, and C). The description may use thephrases “in an embodiment,” or “in embodiments,” which may each refer toone or more of the same or different embodiments. Furthermore, the terms“comprising,” “including,” “having,” and the like, as used with respectto embodiments of the present disclosure, are synonymous.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality.

FIG. 1 schematically illustrates a hybrid management system 100 formanaging both non-virtualized and virtualized networks in accordancewith various embodiments. In some embodiments, the hybrid managementsystem 100 may include a network manager (NM) 102 that may be includedin an operations support system/business support system (OSS/BSS) 104.The OSS/BSS 104 may be in data communication with a network functionvirtualization (NFV) management and orchestration (MANO) system(NFV-MANO) 106 in various embodiments. The NFV-MANO 106 may include anNFV orchestrator (NFVO) 108, a virtual network function (VNF) manager(VNFM) 110, and a virtualized infrastructure manager (VIM) 112 that maybe coupled with and in data communication with each other in variousembodiments. The VNFM 110 may be coupled with and in data communicationwith an element manager (EM) 114 that may be included in a domainmanager (DM) 116. The VNFM 110 may instantiate and/or configure a firstMME VNF 118 and/or a second MME VNF 120 in various embodiments. In someembodiments, an MME VNF may include an EM such as EM 122 shown in MMEVNF 120. The EM 122 may also be coupled with and in data communicationwith the VNFM 110.

In various embodiments, the hybrid management system 100 may include anetwork function virtualization infrastructure (NFVI) 124 that mayinclude hardware resources 126 and a hypervisor 128. The hardwareresources 126 may include various computing resources such as one ormore processors, volatile and/or non-volatile memory, storage,networking, and input/output (IO) resources in various embodiments. Insome embodiments, a virtualization layer in addition to or other than ahypervisor may be used. The EM 114 may be coupled with a network element(NE) physical network function (PNF) 130 such as an MME PNF in variousembodiments. An NE PNF 132 may include an EM 134 that may be coupledwith the OSS/BSS 104 in some embodiments.

FIG. 2 is a diagram illustrating an MME overload mitigation process 200using an MME VNF 202 in accordance with various embodiments. The MME VNF202 may be substantially similar to the MME VNF 118 or the MME VNF 120described with respect to FIG. 1 in various embodiments. An EM 204 maysend performance management (PM) measurements relating to an MME PNF 206in a PM communication 208 to an NM 210 that receives the PMmeasurements. In various embodiments, the PM measurements may includeMME processor usage, S1-MME data volume, or other PM measurements.

The NM 210 may determine that the MME PNF 206 is overloaded based atleast in part on the received PM measurements. The NM 210 may send anMME VNF instantiation request 212 to an NFVO 214 to instantiate a newMME VNF such as the MME VNF 202. The NFVO 214 may perform an MME VNFinstantiation process at a block 216. The NFVO 214 may send an MME VNFinstantiation request 218 to a VNFM 220. The VNFM 220 may instantiatethe MME VNF 202 at a block 222 in response to the instantiation request218.

At a block 224, the MME VNF instantiation request 218 may be validatedand processed. In various embodiments, validation and processing at theblock 224 may include request validation and processing by the VNFM 220.The VNFM 220 may send a resource allocation request 226 to the NFVO 214to request a virtual information manager (VIM) 227 to allocate resourcesrequired by an MME VNF instance. In various embodiments, the NFVO 214may perform pre-allocation processing and send a resource allocationrequest 228 to the VIM 227. In some embodiments, the resource allocationrequest 228 may include compute, storage, network, and/orinterconnection allocation and/or setup parameters. In variousembodiments, the VIM 227 may allocate an internal connectivity network,allocate compute and storage resources of a virtual machine (VM), andattach the VM to the internal connectivity network. The VIM 227 may sendan acknowledgement (Ack) 230 to the NFVO 214 indicating that resourceallocation is completed, and the NFVO 214 may send an Ack 232 to theVNFM 220 indicating that resource allocation is completed.

After the VIM 227 has allocated resources, the VNFM 220 may perform aconfiguration 234 of the MME VNF 202 with lifecycle parameters. The VNFM220 may send a notification 236 to the EM 204, notifying the EM 204 ofthe new MME VNF 202. The VNFM 220 may send an acknowledgement 238 backto the NFVO 214, acknowledging completion of MME VNF instantiation. TheNFVO 214 may send an acknowledgement 240 to the NM 210, acknowledgingthe completion of MME VNF instantiation to the NM 210. The EM 204 mayreceive the notification 236 of the new MME VNF 202 at a block 242. At ablock 244, the EM 204 may configure the MME VNF 202 with applicationspecific parameters. In some embodiments, the parameters may includeapplication parameters such as a weight factor parameter and the EM 204may assign values to the application parameters such as a weight factorfor the weight factor parameter. The application parameters may bereferred to as information elements (IEs) in some embodiments and theweight factor parameter may be referred to as a relative MME capacity IEin various embodiments. In some embodiments, the weight factor may be aninteger that is greater than or equal to zero and less than or equal to255. Alternatively, the weight factor may be a different numerical typeand/or in a different range in some embodiments. In some embodiments,the weight factors allow an evolved node B (eNB) to select an MME toservice a UE in a manner proportional to the relative weight factorsassigned to the MMEs in an MME pool.

At a block 246, the EM 204 may add the MME VNF 202 to a MME pool thatmay include the MME PNF 206. The EM 204 may send a weight factorconfiguration 248 to the MME VNF 202. The EM 204 may send a weightfactor configuration 250 to the MME PNF 206 to assign a weight factor tothe MME PNF 206. In various embodiments, the EM 204 may set the weightfactor configuration 248 to be higher relative to the weight factorconfiguration 250 which may be configured with a relatively low weightfactor to enable UEs such as a UE 254 to choose to connect with the MMEVNF 202 rather than the MME PNF 206 when the UEs are to re-attach to thenetwork. In embodiments, the weight factor configuration 248 may includea first weight factor and the weight factor configuration 250 mayinclude a second weight factor. The weight factor assigned to the MMEVNF 202 may be associated with selection of the MME VNF 202 from aplurality of MMEs of the MME pool to service a UE connection in someembodiments in that the weight factors assigned to the MMEs, includingthe MME VNF 202, may allow an eNB to select an MME to service a UE in amanner proportional to the relative weight factors assigned to the MMEsin the MME pool as mentioned above.

At a block 256, the MME VNF 202, the MME PNF 206, an eNB 251, the UE254, and a home subscriber server (HSS) 257 may run an S1 releaseprocedure 258, a TAU procedure 260, and a location update procedure 262to offload UEs such as the UE 254 to the MME VNF 202. The S1 releaseprocedure 258 may include a first release communication 264 between theUE 254 and the eNB 251 and a second release communication 266 betweenthe eNB and the MME PNF 206 to release the S1 connection. The TAUprocedure 260 may include a first TAU communication 268 between the UE254 and the eNB 251 and a second TAU communication 270 between the eNB251 and the MME VNF 202 that enables UE 254 to select MME VNF 202. Invarious embodiments, the location update procedure 262 may include anupdate location request sent from the MME VNF 202 to the HSS 257 thatmay include information such as MME Identity, international mobilesubscriber identity (IMSI), update location request flags (ULR-Flags),MME Capabilities, Homogenous Support of IP Multimedia Subsystem (IMS)Voice over packet switched (PS) Sessions, UE single radio voice callcontinuity (SRVCC) capability, equivalent public land mobile network(PLMN) list, and/or mobile equipment (ME) Identity (IMEI softwareversion (IMEISV)) in some embodiments.

In various embodiments, components described with respect to FIG. 2 maycorrespond to similar components described with respect to FIG. 1. TheMME VNF 202 may be substantially similar to the MME VNF 118 or the MMEVNF 120 of FIG. 1. The MME PNF 206 of FIG. 2 may correspond to the NEPNF 130 or NE PNF 132 of FIG. 1. The EM 204 may correspond to the EM 114or a combination of EM 122 and 134 in various embodiments. The NM 210,NFVO 214, VNFM 220, and VIM 227 of FIG. 2 may correspond to the NM 102,NFVO 108, VNFM 110, and VIM 112 of FIG. 1, respectively.

FIG. 3 is a diagram illustrating an MME VNF contraction process 300 inaccordance with various embodiments. An EM 302 may send a contractionrequest 304 to a VNFM 306 to release capacity for a MME VNF 308. At ablock 310, the VNFM 306 may perform an MME VNF contraction process alongwith an NFVO 312 and a VIM 314 at a block 316. In various embodiments,the VNFM 306 may send a validation request 318 to the NFVO 312requesting validation for the MME VNF contraction and scale in of theMME VNF using a grant lifecycle operation of a VNF lifecycle operationgranting interface. In some embodiments, the validation request 318 maybe based at least in part on a VNF descriptor (VNFD) associated with theMME VNF 308. The NFVO 312 may take a scaling decision at a block 320 andsend an Ack 322 to the VNFM 306 granting MME VNF contraction.

The VNFM 306 may send an offload request 324 to the EM 302 requestingthe EM 302 to offload UEs from the MME VNF 308 to a neighboring MME 326.At a block 328, the EM 302 may offload the UEs. The EM 302 may send aconfiguration command 330 to the MME VNF 308 configuring MME VNFparameters. In various embodiments, the configuration command 330 mayinclude assigning a low weight factor that may correspond to a relativeMME capacity to the MME VNF 308. In embodiments, the low weight factormay enable UEs such as a UE 332 to choose neighboring MME 326 when theUEs are to re-attach to the network. At a block 334, UEs such as the UE332 may be offloaded from the MME VNF 308 to the MME 326. The UEsassociated with the MME VNF 308, such as the UE 332, and an eNB 336 mayrun an S1 release procedure 338 that may include a first S1 releasecommunication 340 between the UE 332 and the eNB 336 and a second S1release communication 342 between the eNB 336 and the MME VNF 308 torelease the S1 connection. In various embodiments, a TAU procedure 344may be performed by the UEs such as the UE 332 and the eNB 336 tooffload the UEs to a neighboring MME such as the MME 326. The TAUprocedure 344 may include a first TAU communication 346 between the UE332 and the eNB 336 and a second TAU communication 348 between the eNB336 and the MME 326 to enable UE 332 to select MME 326. When all UEs areoffloaded to the MME 326, the MME VNF 308 may send a notification 350 tothe EM 302.

At a block 352, the EM 302 may configure VNF application specificparameters by removing the MME VNF 308 from the MME pool. The EM 302 maysend a notification 354 to the VNFM 306 that no UE is connected to theMME VNF 308. The VNFM 306 may perform a termination process 356 toterminate the MME VNF 308 in response to receiving the notification 354.The VNFM 306 may send a resource release request 358 to the VIM 314. TheVIM 314 may release the resources associated with the MME VNF 308 andsend an Ack 360 to the VNFM 306. The VNFM 306 may send a successfulcontraction notification 362 to the NFVO 312 in response to the Ack 360from the VIM 314. The VNFM 306 may send an Ack 364 to the EM 302 that anexisting VNF has been updated as requested with a capacity release. Invarious embodiments, the EM 302 and the VNFM 306 may perform an update366 of the VNF managed device. In some embodiments, the MME VNF 308 maybe removed from the MME pool in response to a notification that all UEsare offloaded from the MME VNF 308, or in response to a notificationthat the MME VNF 308 is no longer providing services to UEs.

In various embodiments, components described with respect to FIG. 3 maycorrespond to similar components described with respect to FIG. 1. TheMME VNF 308 may be substantially similar to the MME VNF 118 or the MMEVNF 120 of FIG. 1. The MME 326 of FIG. 3 may correspond to the NE PNF130 or NE PNF 132 of FIG. 1. The EM 302 may correspond to the EM 114 ora combination of EM 122 and 134 in various embodiments. The NFVO 312,VNFM 306, and VIM 314 of FIG. 3 may correspond to the NFVO 108, VNFM110, and VIM 112 of FIG. 1, respectively.

FIG. 4 illustrates a device 400 with electronic device circuitry 402that may be eNB circuitry, UE circuitry, MME (VNF) circuitry, MME (PNF)circuitry, MME circuitry, EM circuitry, NFVO circuitry, VNFM circuitry,VIM circuitry, or some other type of circuitry in accordance withvarious embodiments. In embodiments, all or a part of the electronicdevice circuitry 402 may be, or may be incorporated into or otherwise apart of, a eNB such as the eNB 251 or the eNB 336, a UE such as the UE254 or the UE 332, a MME (VNF) such as the MME VNF 202 or the MME VNF308, a MME (PNF) such as the MME PNF 206, a MME such as the MME 326, aEM such as the EM 204 or the EM 302, a NFVO such as the NFVO 214 or theNFVO 312, a VNFM such as the VNFM 220 or the VNFM 306, a VIM such as theVIM 227 or the VIM 314, or some other type of electronic device. Inembodiments, the electronic device circuitry may include radio transmitcircuitry 404 and receive circuitry 406 coupled to control circuitry408. In embodiments, the transmit circuitry 404 and/or receive circuitry406 may be elements or modules of transceiver circuitry, as shown. Theelectronic device circuitry 402 may be coupled with one or moreplurality of antenna elements 410 of one or more antennas. Theelectronic device circuitry 402 and/or the components of the electronicdevice circuitry 402 may be configured to perform operations similar tothose described elsewhere in this disclosure. In some embodiments, theelectronic device circuitry 402 may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules.

The NM 102, OSS/BSS 104, NFV-MANO 106, NFVO 108, VNFM 110, VIM 112, EM114, DM 116, MME VNF 118, MME VNF 120, EM 122, NFVI 124, hardwareresources 126, hypervisor 128, PNF 130, NE PNF 132, EM 134, MME VNF 202,EM 204, MME PNF 206, NM 210, NFVO 214, VNFM 220, VIM 227, eNB 251, UE254, HSS 257, EM 302, VNFM 306, MME VNF 308, NFVO 312, VIM 314, MME 326,UE 332, eNB 336, electronic device circuitry 402, transmit circuitry404, receive circuitry 406, or control circuitry 408, as described inconnection with FIGS. 1-4, may be implemented into a system using anysuitable hardware, firmware, and/or software configured as desired. FIG.5 illustrates, for one embodiment, an example system 500 includingcommunication circuitry such as radio frequency (RF) circuitry 504 andbaseband circuitry 508, application circuitry 512, memory/storage 516,display 520, camera 524, sensor 528, and input/output (I/O) interface532, coupled with each other at least as shown. In various embodiments,some or all of the elements described with respect to the system 500 maybe used to implement one or more of the elements described with respectto FIGS. 1-4. In some embodiments, the communication circuitry mayinclude circuitry in addition to or other than RF circuitry 504 and/orbaseband circuitry 508. In various embodiments, some or all aspectsdescribed with respect to RF circuitry 504 and/or baseband circuitry 508may be performed by other types of communication circuitry.

The application circuitry 512 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Theprocessor(s) may include any combination of general-purpose processorsand dedicated processors (e.g., graphics processors, applicationprocessors, etc.). The processors may be coupled with memory/storage 516and configured to execute instructions stored in the memory/storage 516to enable various applications and/or operating systems running on thesystem 500.

The baseband circuitry 508 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Theprocessor(s) may include a baseband processor. The baseband circuitry508 may include one or more digital signal processors (DSPs) in variousembodiments. The baseband circuitry 508 may handle various radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 504. The radio control functions may include, but arenot limited to, signal modulation, encoding, decoding, radio frequencyshifting, etc. In some embodiments, the baseband circuitry 508 mayprovide for communication compatible with one or more radiotechnologies. For example, in some embodiments, the baseband circuitry508 may support communication with an evolved universal terrestrialradio access network (E-UTRAN) and/or other wireless metropolitan areanetworks (WMAN), a wireless local area network (WLAN), or a wirelesspersonal area network (WPAN). Embodiments in which the basebandcircuitry 508 is configured to support radio communications of more thanone wireless protocol may be referred to as multi-mode basebandcircuitry.

In various embodiments, baseband circuitry 508 may include circuitry tooperate with signals that are not strictly considered as being in abaseband frequency. For example, in some embodiments, baseband circuitry508 may include circuitry to operate with signals having an intermediatefrequency, which is between a baseband frequency and a radio frequency.

RF circuitry 504 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 504 may include switches, filters,amplifiers, etc., to facilitate the communication with the wirelessnetwork.

In various embodiments, RF circuitry 504 may include circuitry tooperate with signals that are not strictly considered as being in aradio frequency. For example, in some embodiments, RF circuitry 504 mayinclude circuitry to operate with signals having an intermediatefrequency, which is between a baseband frequency and a radio frequency.

In various embodiments, transmit circuitry, control circuitry, and/orreceive circuitry discussed or described herein, such as the transmitcircuitry 404, the receive circuitry 406, or the control circuitry 408of FIG. 4, may be embodied in whole or in part in one or more of the RFcircuitry 504, the baseband circuitry 508, and/or the applicationcircuitry 512.

In some embodiments, some or all of the constituent components of thebaseband circuitry 508, the application circuitry 512, and/or thememory/storage 516 may be implemented together on a system on a chip(SOC).

Memory/storage 516 may be used to load and store data and/orinstructions, for example, for system 500. Memory/storage 516 for oneembodiment may include any combination of suitable volatile memory(e.g., dynamic random access memory (DRAM)) and/or non-volatile memory(e.g., Flash memory).

In various embodiments, the I/O interface 532 may include one or moreuser interfaces to enable user interaction with the system 500 and/orperipheral component interfaces to enable peripheral componentinteraction with the system 500. User interfaces may include, but arenot limited to, a physical keyboard or keypad, a touchpad, a speaker, amicrophone, etc. Peripheral component interfaces may include, but arenot limited to, a non-volatile memory port, a universal serial bus (USB)port, an audio jack, and a power supply interface.

In various embodiments, sensor 528 may include one or more sensingdevices to determine environmental conditions and/or locationinformation related to the system 500. In some embodiments, the sensorsmay include, but are not limited to, a gyro sensor, an accelerometer, aproximity sensor, an ambient light sensor, and a positioning unit. Thepositioning unit may also be part of, or interact with, the basebandcircuitry 508 and/or RF circuitry 504 to communicate with components ofa positioning network, e.g., a global positioning system (GPS)satellite.

In various embodiments, the display 520 may include a display, e.g., aliquid crystal display, a touch screen display, etc. In variousembodiments, the system 500 may be a mobile computing device such as,but not limited to, a laptop computing device, a tablet computingdevice, a netbook, an ultrabook, a smartphone, etc. In variousembodiments, system 500 may have more or fewer components, and/ordifferent architectures.

Embodiments of the technology herein may be described as related to thethird generation partnership project (3GPP) long term evolution (LTE) orLTE-advanced (LTE-A) standards. For example, terms or entities such aseNodeB (eNB), mobility management entity (MME), user equipment (UE),etc. may be used that may be viewed as LTE-related terms or entities.However, in other embodiments the technology may be used in or relatedto other wireless technologies such as the Institute of Electrical andElectronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE802.11 wireless technology (WiFi), various other wireless technologiessuch as global system for mobile communications (GSM), enhanced datarates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN),universal mobile telecommunications system (UMTS), UMTS terrestrialradio access network (UTRAN), or other 2G, 3G, 4G, 5G, etc. technologieseither already developed or to be developed. In those embodiments, whereLTE-related terms such as eNB, MME, UE, etc. are used, one or moreentities or components may be used that may be considered to beequivalent or approximately equivalent to one or more of the LTE-basedterms or entities.

FIG. 6 illustrates an article of manufacture 610 having programminginstructions, incorporating aspects of the present disclosure, inaccordance with various embodiments. In various embodiments, an articleof manufacture may be employed to implement various embodiments of thepresent disclosure. As shown, the article of manufacture 610 may includea computer-readable non-transitory storage medium 620 where instructions630 may be configured to practice embodiments of or aspects ofembodiments of any one of the processes described herein. The storagemedium 620 may represent a broad range of persistent storage media knownin the art, including but not limited to flash memory, dynamic randomaccess memory, static random access memory, an optical disk, a magneticdisk, etc. In embodiments, computer-readable storage medium 620 mayinclude one or more computer-readable non-transitory storage media. Inother embodiments, computer-readable storage medium 620 may betransitory, such as signals, encoded with instructions 630.

In various embodiments, instructions 630 may enable an apparatus, inresponse to its execution by the apparatus, to perform variousoperations described herein. As an example, storage medium 620 mayinclude instructions 630 configured to cause an apparatus or module,e.g., NM 102, OSS/BSS 104, NFV-MANO 106, NFVO 108, VNFM 110, VIM 112, EM114, DM 116, MME VNF 118, MME VNF 120, EM 122, NFVI 124, hardwareresources 126, hypervisor 128, PNF 130, NE PNF 132, EM 134, MME VNF 202,EM 204, MME PNF 206, NM 210, NFVO 214, VNFM 220, VIM 227, eNB 251, UE254, HSS 257, EM 302, VNFM 306, MME VNF 308, NFVO 312, VIM 314, MME 326,UE 332, eNB 336, electronic device circuitry 402, transmit circuitry404, receive circuitry 406, control circuitry 408, system 500, RFcircuitry 504, baseband circuitry 508, or application circuitry 512 asdescribed in connection with FIGS. 1-5, to practice some aspects of MMEoverload or underload mitigation using an MME VNF, e.g., as illustratedin MME overload mitigation process 200 of FIG. 2 or MME VNF contractionprocess 300 of FIG. 3, in accordance with embodiments of the presentdisclosure.

The following paragraphs describe examples of various embodiments.

Example 1 may include an element manager (EM) comprising: one or morestorage media having instructions; and one or more processors, coupledwith the one or more storage media to execute the instructions to:process a notification from a virtual network function manager (VNFM) todetermine instantiation of a mobility management entity (MME) as avirtual network function (VNF); add the MME VNF to an MME pool; andassign a value to an application parameter of the MME VNF.

Example 2 may include the subject matter of Example 1, wherein theapplication parameter is a weight factor parameter and the value is aweight factor, wherein the weight factor is associated with selection ofthe MME VNF from a plurality of MMEs of the MME pool to service a userequipment (UE) connection.

Example 3 may include the subject matter of any one of Examples 1-2,wherein the one or more processors are further to execute theinstructions to add the MME VNF to the MME pool in response to anotification that the MME VNF has been instantiated.

Example 4 may include the subject matter of Example 3, wherein the oneor more processors are further to execute the instructions to: determinea performance management (PM) measurement of a MME physical networkfunction (PNF); send the PM measurement to a network manager; andreceive the notification that the MME VNF has been instantiated inresponse to the send of the PM measurement.

Example 5 may include the subject matter of Example 4, wherein the PMmeasurement includes an MME processor usage measurement.

Example 6 may include the subject matter of Example 4, wherein the PMmeasurement includes an S1-MME data volume measurement.

Example 7 may include the subject matter of any one of Examples 2-6,wherein the weight factor is a first weight factor and the one or moreprocessors are further to execute the instructions to assign a secondweight factor to an MME physical network function (PNF), wherein thesecond weight factor is lower than the first weight factor.

Example 8 may include the subject matter of Example 7, wherein the oneor more processors are further to execute the instructions to assign anupdated first weight factor to the MME VNF in response to a request tooffload user equipments (UEs) from the MME VNF, wherein the updatedfirst weight factor is lower than the first weight factor.

Example 9 may include the subject matter of any of Examples 7-8, whereinthe one or more processors are further to execute the instructions toremove the MME VNF from the MME pool in response to a notification thatall UEs are offloaded from the MME VNF, or the MME VNF is no longerproviding services to UEs.

Example 10 may include the subject matter of Example 9, wherein the oneor more processors are further to execute the instructions to send anotification to a virtual network function manager (VNFM) that no UE isconnected to the MME VNF.

Example 11 may include the subject matter of any one of Examples 2-6,wherein the weight factor is a first weight factor and the processingcircuitry is also to assign a second weight factor to a second MME VNFin the MME pool, wherein the first weight factor is higher than thesecond weight factor.

Example 12 may include the subject matter of any one of Examples 2-11,wherein the MME pool is in a long term evolution (LTE) environment.

Example 13 may include a network function virtualization orchestrator(NFVO) comprising: one or more storage media having instructions; andone or more processors, coupled with the one or more storage media toexecute the instructions to: process a virtual network function (VNF)instantiation request from a network manager (NM); and direct a virtualnetwork function manager (VNFM) to instantiate a mobility managemententity (MME) VNF in response to the VNF instantiation request.

Example 14 may include the subject matter of Example 13 wherein the oneor more processors are further to execute the instructions to send aresource allocation request to a virtualized infrastructure manager(VIM).

Example 15 may include the subject matter of Example 14, wherein theresource allocation request includes at least one of a computeallocation parameter or a storage allocation parameter.

Example 16 may include the subject matter of any one of Examples 13-15,wherein the one or more processors are further to execute theinstructions to send an acknowledgement to the NM indicating MME VNFinstantiation is completed.

Example 17 may include a virtual network function manager (VNFM)comprising: one or more storage media having instructions; and one ormore processors, coupled with the one or more storage media to executethe instructions to: process an instantiation request for a mobilitymanagement entity (MME) virtual network function (VNF) from a networkfunction virtualization orchestrator (NFVO); send a resource allocationrequest to the NFVO in response to the instantiation request; andconfigure a MME VNF.

Example 18 may include the subject matter of Example 17, wherein the oneor more processors are further to execute the instructions to send anotification to an element manager (EM) notifying the EM of the MME VNF.

Example 19 may include the subject matter of any one of Examples 17-18,wherein the one or more processors are further to execute theinstructions to send an acknowledgement to the NFVO indicatingcompletion of MME VNF instantiation.

Example 20 may include the subject matter of any one of Examples 17-19,wherein the one or more processors are further to execute theinstructions to process a request from an EM to release capacity for theMME VNF and send an offload request to the EM requesting the EM tooffload user equipments (UEs) from the MME VNF.

Example 21 may include the subject matter of Example 20, wherein the oneor more processors are further to execute the instructions to perform atermination process to terminate the MME VNF in response to anotification from the EM that no UE is connected to the MME VNF.

Example 22 may include the subject matter of Example 21, wherein the oneor more processors are further to execute the instructions to send anacknowledgement to the EM that an existing VNF has been updated asrequested with a capacity release.

Example 23 may include a network manager (NM) comprising: one or morestorage media having instructions; and one or more processors, coupledwith the one or more storage media to execute the instructions to:process performance management (PM) measurements for a mobilitymanagement entity (MME) from an element manager (EM); determine that theMME is overloaded in response to a PM measurement above a predefinedthreshold level; and send a MME virtual network function (VNF)instantiation request to a network function virtualization orchestrator(NFVO).

Example 24 may include the subject matter of Example 23, wherein the oneor more processors are to determine that the MME is overloaded inresponse to MME processor usage above a predefined threshold level.

Example 25 may include the subject matter of Example 23, wherein the oneor more processors are to determine that the MME is overloaded inresponse to S1-MME data volume above a predefined threshold level.

Example 26 may include a method of controlling mobility managemententity (MME) load status comprising: processing a notification from avirtual network function manager (VNFM) to determine instantiation of amobility management entity (MME) as a virtual network function (VNF);adding the MME VNF to an MME pool; and assigning a value to anapplication parameter of the MME VNF.

Example 27 may include the subject matter of Example 26, wherein theapplication parameter is a weight factor parameter and the value is aweight factor, wherein the weight factor is associated with selection ofthe MME VNF from a plurality of MMEs of the MME pool to service a userequipment (UE) connection.

Example 28 may include the subject matter of any one of Examples 26-27,wherein adding the MME VNF to the MME pool is in response to anotification that the MME VNF has been instantiated.

Example 29 may include the subject matter of Example 28, furthercomprising: determining a performance management (PM) measurement of aMME physical network function (PNF); sending the PM measurement to anetwork manager; and receiving the notification that the MME VNF hasbeen instantiated in response to the send of the PM measurement.

Example 30 may include the subject matter of Example 29, wherein the PMmeasurement includes an MME processor usage measurement.

Example 31 may include the subject matter of Example 29, wherein the PMmeasurement includes an S1-MME data volume measurement.

Example 32 may include the subject matter of any one of Examples 27-31,wherein the weight factor is a first weight factor and the methodfurther comprises assigning a second weight factor to an MME physicalnetwork function (PNF), wherein the second weight factor is lower thanthe first weight factor.

Example 33 may include the subject matter of Example 32, furthercomprising assigning an updated first weight factor to the MME VNF inresponse to a request to offload user equipments (UEs) from the MME VNF,wherein the updated first weight factor is lower than the first weightfactor.

Example 34 may include the subject matter of any one of Examples 32-33,further comprising removing the MME VNF from the MME pool in response toa notification that all UEs are offloaded from the MME VNF.

Example 35 may include the subject matter of Example 34, furthercomprising sending a notification to a virtual network function manager(VNFM) that no UE is connected to the MME VNF.

Example 36 may include the subject matter of any one of Examples 27-31,wherein the weight factor is a first weight factor and the methodfurther includes assigning a second weight factor to a second MME VNF inthe MME pool, wherein the first weight factor is higher than the secondweight factor.

Example 37 may include the subject matter of any one of Examples 27-36,wherein the MME pool is in a long term evolution (LTE) environment.

Example 38 may include a method comprising: processing a virtual networkfunction (VNF) instantiation request from a network manager (NM); anddirecting a virtual network function manager (VNFM) to instantiate amobility management entity (MME) VNF in response to the VNFinstantiation request.

Example 39 may include the subject matter of Example 38, furthercomprising sending a resource allocation request to a virtualizedinfrastructure manager (VIM).

Example 40 may include the subject matter of Example 39, wherein theresource allocation request includes at least one of a computeallocation parameter or a storage allocation parameter.

Example 41 may include the subject matter of any one of Examples 38-40,further comprising sending an acknowledgement to the NM indicating MMEVNF instantiation is completed.

Example 42 may include a method comprising: processing an instantiationrequest for a mobility management entity (MME) virtual network function(VNF) from a network function virtualization orchestrator (NFVO);sending a resource allocation request to the NFVO in response to theinstantiation request; and configuring a MME VNF.

Example 43 may include the subject matter of Example 42, furthercomprising sending a notification to an element manager (EM) notifyingthe EM of the MME VNF.

Example 44 may include the subject matter of any one of Examples 42-43,further comprising sending an acknowledgement to the NFVO indicatingcompletion of MME VNF instantiation.

Example 45 may include the subject matter of any one of Examples 42-44,further comprising processing a request from an EM to release capacityfor the MME VNF and sending an offload request to the EM requesting theEM to offload user equipments (UEs) from the MME VNF.

Example 46 may include the subject matter of Example 45, furthercomprising performing a termination process to terminate the MME VNF inresponse to a notification from the EM that no UE is connected to theMME VNF.

Example 47 may include the subject matter of Example 46, furthercomprising sending an acknowledgement to the EM that an existing VNF hasbeen updated as requested with a capacity release.

Example 48 may include a method comprising: processing performancemanagement (PM) measurements for a mobility management entity (MME) froman element manager (EM); determining that the MME is overloaded inresponse to a PM measurement above a predefined threshold level; andsending a MME virtual network function (VNF) instantiation request to anetwork function virtualization orchestrator (NFVO).

Example 49 may include the subject matter of Example 48, wherein the PMmeasurement includes a MME processor usage measurement.

Example 50 may include the subject matter of Example 48, wherein the PMmeasurement includes a S1-MME data volume measurement.

Example 51 may include an apparatus for controlling mobility managemententity (MME) load status comprising: means for processing a notificationfrom a virtual network function manager (VNFM) to determineinstantiation of a mobility management entity (MME) as a virtual networkfunction (VNF); means for adding the MME VNF to an MME pool; and meansfor assigning a value to an application parameter of the MME VNF.

Example 52 may include the subject matter of Example 51, wherein theapplication parameter is a weight factor parameter and the value is aweight factor, wherein the weight factor is associated with selection ofthe MME VNF from a plurality of MMEs of the MME pool to service a userequipment (UE) connection.

Example 53 may include the subject matter of any one of Examples 51-52,wherein means for adding the MME VNF to the MME pool is to add the MMEVNF to the MME pool in response to a notification that the MME VNF hasbeen instantiated.

Example 54 may include the subject matter of Example 53, furthercomprising: means for determining a performance management (PM)measurement of a MME physical network function (PNF); means for sendingthe PM measurement to a network manager; and means for receiving thenotification that the MME VNF has been instantiated in response to thesend of the PM measurement.

Example 55 may include the subject matter of Example 54, wherein the PMmeasurement includes an MME processor usage measurement.

Example 56 may include the subject matter of Example 54, wherein the PMmeasurement includes an S1-MME data volume measurement.

Example 57 may include the subject matter of any one of Examples 52-56,wherein the weight factor is a first weight factor and the apparatusfurther comprises means for assigning a second weight factor to an MMEphysical network function (PNF), wherein the second weight factor islower than the first weight factor.

Example 58 may include the subject matter of Example 57, furthercomprising means for assigning an updated first weight factor to the MMEVNF in response to a request to offload user equipments (UEs) from theMME VNF, wherein the updated first weight factor is lower than the firstweight factor.

Example 59 may include the subject matter of any one of Examples 57-58,further comprising means for removing the MME VNF from the MME pool inresponse to a notification that all UEs are offloaded from the MME VNF.

Example 60 may include the subject matter of Example 59, furthercomprising means for sending a notification to a virtual networkfunction manager (VNFM) that no UE is connected to the MME VNF.

Example 61 may include the subject matter of any one of Examples 52-56,wherein the weight factor is a first weight factor and the apparatusfurther includes means for assigning a second weight factor to a secondMME VNF in the MME pool, wherein the first weight factor is higher thanthe second weight factor.

Example 62 may include the subject matter of any one of Examples 52-61,wherein the MME pool is in a long term evolution (LTE) environment.

Example 63 may include an apparatus for controlling mobility managemententity (MME) load status comprising: means for processing a virtualnetwork function (VNF) instantiation request from a network manager(NM); and means for directing a virtual network function manager (VNFM)to instantiate a mobility management entity (MME) VNF in response to theVNF instantiation request.

Example 64 may include the subject matter of Example 63, furthercomprising means for sending a resource allocation request to avirtualized infrastructure manager (VIM).

Example 65 may include the subject matter of Example 64, wherein theresource allocation request includes at least one of a computeallocation parameter or a storage allocation parameter.

Example 66 may include the subject matter of any one of Examples 63-65,further comprising means for sending an acknowledgement to the NMindicating MME VNF instantiation is completed.

Example 67 may include an apparatus for controlling mobility managemententity (MME) load status comprising: means for processing aninstantiation request for a mobility management entity (MME) virtualnetwork function (VNF) from a network function virtualizationorchestrator (NFVO); mean for sending a resource allocation request tothe NFVO in response to the instantiation request; and means forconfiguring a MME VNF.

Example 68 may include the subject matter of Example 67, furthercomprising means for sending a notification to an element manager (EM)notifying the EM of the MME VNF.

Example 69 may include the subject matter of any one of Examples 67-68,further comprising means for sending an acknowledgement to the NFVOindicating completion of MME VNF instantiation.

Example 70 may include the subject matter of any one of Examples 67-69,further comprising means for processing a request from an EM to releasecapacity for the MME VNF and means for sending an offload request to theEM requesting the EM to offload user equipments (UEs) from the MME VNF.

Example 71 may include the subject matter of Example 70, furthercomprising means for performing a termination process to terminate theMME VNF in response to a notification from the EM that no UE isconnected to the MME VNF.

Example 72 may include the subject matter of Example 71, furthercomprising means for sending an acknowledgement to the EM that anexisting VNF has been updated as requested with a capacity release.

Example 73 may include an apparatus for controlling mobility managemententity (MME) load status comprising: means for processing performancemanagement (PM) measurements for a mobility management entity (MME) froman element manager (EM); means for determining that the MME isoverloaded in response to a PM measurement above a predefined thresholdlevel; and means for sending a MME virtual network function (VNF)instantiation request to a network function virtualization orchestrator(NFVO).

Example 74 may include the subject matter of Example 73, wherein the PMmeasurement includes a MME processor usage measurement.

Example 75 may include the subject matter of Example 73, wherein the PMmeasurement includes a S1-MME data volume measurement.

Example 76 may include a hybrid management system comprising: a virtualnetwork function manager (VNFM); and an element manager (EM) having: oneor more storage media having instructions; and one or more processors,coupled with the one or more storage media to execute the instructionsto: process a notification from the VNFM to determine instantiation of amobility management entity (MME) as a virtual network function (VNF);add the MME VNF to an MME pool; and assign a value to an applicationparameter of the MME VNF.

Example 77 may include the subject matter of Example 76, wherein theapplication parameter is a weight factor parameter and the value is aweight factor, wherein the weight factor is associated with selection ofthe MME VNF from a plurality of MMEs of the MME pool to service a userequipment (UE) connection.

Example 78 may include the subject matter of any one of Examples 76-77,wherein the one or more processors are further to execute theinstructions to add the MME VNF to the MME pool in response to anotification that the MME VNF has been instantiated.

Example 79 may include the subject matter of Example 78, wherein the oneor more processors are further to execute the instructions to: determinea performance management (PM) measurement of a MME physical networkfunction (PNF); send the PM measurement to a network manager; andreceive the notification that the MME VNF has been instantiated inresponse to the send of the PM measurement.

Example 80 may include the subject matter of Example 79, wherein the PMmeasurement includes an MME processor usage measurement.

Example 81 may include the subject matter of Example 79, wherein the PMmeasurement includes an S1-MME data volume measurement.

Example 82 may include the subject matter of any one of Examples 77-81,wherein the weight factor is a first weight factor and the one or moreprocessors are further to execute the instructions to assign a secondweight factor to an MME physical network function (PNF), wherein thesecond weight factor is lower than the first weight factor.

Example 83 may include the subject matter of Example 82, wherein the oneor more processors are further to execute the instructions to assign anupdated first weight factor to the MME VNF in response to a request tooffload user equipments (UEs) from the MME VNF, wherein the updatedfirst weight factor is lower than the first weight factor.

Example 84 may include the subject matter of any one of Examples 82-83,wherein the one or more processors are further to execute theinstructions to remove the MME VNF from the MME pool in response to anotification that all UEs are offloaded from the MME VNF.

Example 85 may include the subject matter of Example 84, wherein the oneor more processors are further to execute the instructions to send anotification to a virtual network function manager (VNFM) that no UE isconnected to the MME VNF.

Example 86 may include the subject matter of any one of Examples 77-81,wherein the weight factor is a first weight factor and the processingcircuitry is also to assign a second weight factor to a second MME VNFin the MME pool, wherein the first weight factor is higher than thesecond weight factor.

Example 87 may include the subject matter of any one of Examples 77-86,wherein the MME pool is in a long term evolution (LTE) environment.

Example 88 may include an apparatus, method, or system comprising one ormore of: a Network Manager (NM) to perform the network managementfunction to manage one or more third generation partnership project(3GPP) networks directly or via an element manager (EM); a virtualizednetwork function (VNF) Manager (VNFM) to perform lifecycle management ofa VNF; wherein the EM is to perform an element management functionrelated to management of virtualized network elements such as a mobilitymanagement entity (MME) VNF and non-virtualized network elements such asan MME physical network function (PNF) or a serving gateway (SGW); anetwork functions virtualization (NFV) orchestrator (NFVO) to performorchestration of network resources and lifecycle management of networkservices; a virtualized infrastructure manager (VIM) to be responsiblefor the resource allocation and de-allocation; wherein the MME (VNF) isto perform a virtualized MME function; and wherein the MME (PNF) is toperform a non-virtualized MME function.

Example 89 may include the apparatus, method, or system of example 88 orsome other example herein, wherein the NM is to receive one or more MMEperformance management (PM) measurements such as MME processor usageand/or S1-MME data volume from the EM, and detect that the MME (PNF)and/or MME (VNF) is overloaded based on monitoring of the PMmeasurements.

Example 90 may include the apparatus, method, or system of any ofexamples 88-89, or some other example herein, wherein the NM is to senda request to the NFVO to instantiate a new MME (VNF) to compensate theoverloaded MME identified in Example 89.

Example 91 may include the apparatus, method, or system of any ofexamples 88-90, or some other example herein, wherein the NFVO is tocall the VNFM to instantiate the MME (VNF).

Example 92 may include the apparatus, method, or system of any ofexamples 88-91, or some other example herein, wherein the VNFM isfurther to validate and process the instantiation request, and thenrequest the NFVO to allocate the resources required by the MME VNFinstance; the NFVO is to request the VIM to allocate the resources suchas one or more of compute resources, storage resources, networkresources, and/or some other type of resources; the VIM is to allocatethe one or more resources and send an acknowledgement to the NFVO whenthe resource allocation is complete; and the NFVO is to forward theresource allocation acknowledgement to the VNFM.

Example 93 may include the apparatus, method, or system of any ofexamples 88-92, or some other example herein, wherein the VNFM isfurther to: transmit a request to the EM to configure the MME (VNF) withany VNF specific lifecycle parameters after the successful resourcesallocation by VIM; transmit a notification of the new MME (VNF) to theEM that will configure the MME (VNF) with application specificparameters; transmit an acknowledgement of the completion of VNFinstantiation to the NFVO that forwards the acknowledgement of thecompletion of VNF instantiation to NM.

Example 94 may include the apparatus, method, or system of any ofexamples 88-93, or some other example herein, wherein the EM is furtherto add the MME (VNF) to the MME pool; configure a high weight factorsuch as relative MME capacity to the MME (VNF); and configure a lowweight factor such as relative MME capacity to the MME (PNF) that ismuch lower than the weight factor of MME (VNF) to enable a userequipment (UE) to choose the MME (VNF) when one or more UEs are tore-attach to the network.

Example 95 may include the apparatus, method, or system of any ofexamples 88-94 or some other example herein, wherein the MME (PNF) is tooffload one or more UEs to the MME (VNF) by first initiating a S1release procedure with release cause “load balancing tracking areaupdate (TAU) required” that will release one or more radio resourcecontrol (RRC) connections, and secondly after the RRC connections arereleased, an evolved NodeB (eNB) will request that the UE to initiate aTAU without providing the s-temporary mobile subscriber identity(S-TMSI) and/or the globally unique mobility management entityidentifier (GUMMEI) to the eNB in RRC establishment; the UE is toinitiate a TAU based on the RRC connection release with release cause“load re-balancing TAU required” to connect to the MME (VNF); and theMME (VNF) is to send the Update Location Request to a home subscriberserver (HSS) to perform the location update.

Example 96 may include the apparatus, method, or system of example 88,or some other example herein, wherein the EM is to send a request to theVNFM to release the capacity for the MME (VNF), when the MME (VNF) iswasting capacity that is needed.

Example 97 may include the apparatus, method, or system of example 96 orsome other example herein, wherein the VNFM requests a grant of VNFcontraction from the NFVO.

Example 98 may include the apparatus, method, or system of any ofexamples 96-97 or some other example herein, wherein the NFVO is todetermine to grant the VNFM to perform the VNF contraction, and send anacknowledgement to the VNFM.

Example 99 may include the apparatus, method, or system of any ofexamples 96-98 or some other example herein, wherein the VNFM is torequest the EM to offload UEs from MME (VNF) to a neighboring MME.

Example 100 may include the apparatus, method, or system of any ofexamples 96-99, or some other example herein, wherein the EM is toconfigure the VNF application specific parameters by assigning assign ahigher weight factor such as Relative MME Capacity, the MME (VNF) willoffload UEs to the neighboring MME by first initiating the S1 releaseprocedure with release cause “load balancing TAU required” that willrelease RRC connections, and secondly after the RRC connections arereleased, eNB will request the UE to initiate a TAU without providingneither the S-TMSI nor the GUMMEI to eNodeB in the RRC establishment,the UE initiates a TAU due to RRC connection release with release cause“load re-balancing TAU required” to connect to MME (VNF), the MME (VNF)notifies EM when all UE are offloaded to neighboring MME, the EMconfigures the VNF application specific parameters by removing the MME(VNF) from the MME pool, and the EM notifies VNFM that no UE isconnected to MME (VNF).

Example 101 may include the apparatus, method, or system of any ofexamples 96-100 or some other example herein, wherein the VNFM isfurther to: terminate the MME (VNF) instance, request the VIM to releaseresources, report the successful VNF contraction to NFVO after theresources being successful released by VIM, and acknowledge to EM thatan existing VNF has been updated as requested with capacity release.

Example 102 may include the apparatus, method, or system of any ofexamples 96-101 or some other example herein, wherein the EM and theVNFM are to update the MME (VNF) managed device.

Example 103 may include the apparatus, method, or system of example 88or some other example herein, wherein the NFVO is to receive a requestto instantiate a new VNF from the NM, and call the VNFM to instantiatethe VNF.

Example 104 may include the apparatus, method, or system of example 103or some other example herein, wherein the VNFM is to request the VIM toallocate the resources required by the VNF instance.

Example 105 may include the apparatus, method, or system of any ofexamples 103-104 or some other example herein, wherein the VNFM isfurther to configure the VNF with any VNF specific lifecycle parameters,the VNFM is further to notify the EM of the new VNF, the EM is furtherto configure the VNF with application specific parameters, and the VNFMis further to send an acknowledgement of the completion of the VNFinstantiation to NFVO.

Example 106 may include the apparatus, method, or system of any ofexamples 103-105 or some other example herein, wherein the NFVO is toacknowledge the completion of the VNF instantiation to NM.

Example 107 may include the apparatus, method, or system of example 88or some other example herein, wherein the EM is to send a request torelease the capacity of the VNF to the VNFM, or the NM, via the EM, isto send a request to release the capacity of the VNF to the VNFM, or theVNFM is to decide to initiate VNF contraction.

Example 108 may include the apparatus, method, or system of example 107or some other example herein, wherein the VNFM is to request the VNF togracefully terminate a VNF component prior to VNF instance contraction.

Example 109 may include the apparatus, method, or system of any ofexamples 107-108 or some other example herein, wherein the VNFM requeststhe VIM to delete the VM(s), after the VNF component is gracefullyterminated.

Example 110 may include the apparatus, method, or system of any ofexamples 107-109 or some other example herein, wherein the VNFM maynotify the EM that an existing VNF has been updated with requestedcapacity reduction, after VIM acknowledging the successful resourcesrelease, and may notify EM or NM if the contraction is triggered by EMor NM.

Example 111 may include the apparatus, method, or system of any ofexamples 107-110 or some other example herein, wherein EM and VNFMupdates the VNF managed device.

Example 112 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples88-111, or any other method or process described herein.

Example 113 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 88-111, or any other method or processdescribed herein.

Example 114 may include an apparatus comprising control circuitry,transmit circuitry, and/or receive circuitry to perform one or moreelements of a method described in or related to any of examples 88-111,or any other method or process described herein.

Example 115 may include a method of communicating in a wireless networkas shown and described herein.

Example 116 may include a system for providing wireless communication asshown and described herein.

Example 117 may include a device for providing wireless communication asshown and described herein.

The description herein of illustrated implementations, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe present disclosure to the precise forms disclosed. While specificimplementations and examples are described herein for illustrativepurposes, a variety of alternate and/or equivalent embodiments orimplementations calculated to achieve the same purposes may be made inlight of the above detailed description, without departing from thescope of the present disclosure, as those skilled in the relevant artwill recognize.

What is claimed is:
 1. An element manager (EM) comprising: one or morestorage media having instructions; and one or more processors, coupledwith the one or more storage media to execute the instructions to:process a notification from a virtual network function manager (VNFM) todetermine instantiation of a mobility management entity (MME) as avirtual network function (VNF); add the MME VNF to an MME pool; andassign a value to an application parameter of the MME VNF.
 2. The EM ofclaim 1, wherein the application parameter is a weight factor parameterand the value is a weight factor, wherein the weight factor isassociated with selection of the MME VNF from a plurality of MMEs of theMME pool to service a user equipment (UE) connection.
 3. The EM of claim2, wherein the one or more processors are further to execute theinstructions to add the MME VNF to the MME pool in response to anotification that the MME VNF has been instantiated.
 4. The EM of claim3, wherein the one or more processors are further to execute theinstructions to: determine a performance management (PM) measurement ofan MME physical network function (PNF); send the PM measurement to anetwork manager; and receive the notification that the MME VNF has beeninstantiated in response to the send of the PM measurement.
 5. The EM ofclaim 4, wherein the PM measurement includes an MME processor usagemeasurement.
 6. The EM of claim 4, wherein the PM measurement includesan S1-MME data volume measurement.
 7. The EM of claim 2, wherein theweight factor is a first weight factor and the one or more processorsare further to execute the instructions to assign a second weight factorto an MME physical network function (PNF), wherein the second weightfactor is lower than the first weight factor.
 8. The EM of claim 7,wherein the one or more processors are further to execute theinstructions to assign an updated first weight factor to the MME VNF inresponse to a request to offload user equipments (UEs) from the MME VNF,wherein the updated first weight factor is lower than the first weightfactor.
 9. The EM of claim 7, wherein the one or more processors arefurther to execute the instructions to remove the MME VNF from the MMEpool in response to a notification that all UEs are offloaded from theMME VNF, or the MME VNF is no longer providing services to UEs.
 10. TheEM of claim 9, wherein the one or more processors are further to executethe instructions to send a notification to a virtual network functionmanager (VNFM) that no UE is connected to the MME VNF.
 11. The EM ofclaim 2, wherein the weight factor is a first weight factor and the oneor more processors are further to execute the instructions to assign asecond weight factor to a second MME VNF in the MME pool, wherein thefirst weight factor is higher than the second weight factor.
 12. The EMof claim 2, wherein the MME pool is in a long term evolution (LTE)environment.
 13. A virtual network function manager (VNFM) comprising:one or more storage media having instructions; and one or moreprocessors, coupled with the one or more storage media to execute theinstructions to: process an instantiation request for a mobilitymanagement entity (MME) virtual network function (VNF) from a networkfunction virtualization orchestrator (NFVO); send a resource allocationrequest to the NFVO in response to the instantiation request; configurean MME VNF; and send a notification to an element manager (EM) notifyingthe EM of the MME VNF.
 14. The VNFM of claim 13, wherein the one or moreprocessors are further to execute the instructions to send anacknowledgement to the NFVO indicating completion of MME VNFinstantiation.
 15. The VNFM of claim 13, wherein the one or moreprocessors are further to execute the instructions to process a requestfrom an EM to release capacity for the MME VNF and send an offloadrequest to the EM requesting the EM to offload user equipments (UEs)from the MME VNF.
 16. The VNFM of claim 15, wherein the one or moreprocessors are further to execute the instructions to perform atermination process to terminate the MME VNF in response to anotification from the EM that no UE is connected to the MME VNF.
 17. TheVNFM of claim 16, wherein the one or more processors are further toexecute the instructions to send an acknowledgement to the EM that anexisting VNF has been updated as requested with a capacity release. 18.A network manager (NM) comprising: one or more storage media havinginstructions; and one or more processors, coupled with the one or morestorage media to execute the instructions to: process performancemanagement (PM) measurements for a mobility management entity (MME)physical network function (PNF) from an element manager (EM); determinethat the MME PNF is overloaded in response to a PM measurement above apredefined threshold level; and send an MME virtual network function(VNF) instantiation request to a network function virtualizationorchestrator (NFVO).
 19. The NM of claim 18, wherein the one or moreprocessors are to determine that the MME PNF is overloaded in responseto MME processor usage above a predefined threshold level.
 20. The NM ofclaim 18, wherein the one or more processors are to determine that theMME PNF is overloaded in response to S1-MME data volume above apredefined threshold level.